

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
<script type="text/javascript" src="helpman_topicinit.js"></script>

<title>Stereotypes Profiles [Enterprise Architect User Guide]</title>

<meta name="keywords" content="Enterprise Architect, Sparx Systems, UML, Profile,Profile Stereotype,Stereotype,Stereotype Profile">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<meta http-equiv="Content-Style-Type" content="text/css" />

<link type="text/css" href="default.css" rel="stylesheet" />
<style type="text/css">
  A, A:Visited
  {
    color: #00F;
  }

  A:Active, A:Hover
  {
    color: #F00;
  }

  OL
  {
    margin: 5px 0 5px 48px;
  }

  UL
  {
    margin-bottom: 3px;
    margin-top: 0;
  }

  #nsr
  {
    background-color: #D4DFFF;
  }

  #nsr A
  {
    text-decoration: none;
  }

  #mainbody
  {
    padding: 8px;
  }

  .p_BodyText
  {
    padding: 5px 0;
  }
</style>



<style type="text/css" media="screen">
  BODY
  {
    background-color: #FFFFFF;
  }

  #nsr
  {
    padding: 6px 6px 0 6px;
    border-bottom: none;
    vertical-align: top;
    z-index: 2;
    visibility: visible;
    left: 0;
    top: 0;
    position: absolute;
  }

  #mainbody
  {
    left: 0;
    top: 0;
    margin: 0;
    position: absolute;
    padding: 10px;
    overflow: auto;
    height: 100%;
    z-index: 1;
    background-repeat: no-repeat;
    background-position: bottom right;
    background-attachment: fixed;
  }
</style>

<style type="text/css" media="print">
  #nsr
  {
    visibility: none;
  }

  #mainbody
  {
    overflow: visible;
  }
</style>
<script type="text/javascript" language="JavaScript" src="nonscroll.js"></script>

</head>
<body scroll="no">

<div id="page">



        <div id="content">
          <div id="content-inner">
          



  
          <div id="nsr">
            <table border="0" cellspacing="0" cellpadding="4" width="100%">
              <tr valign="top">
                <td align="left">
  


                  <p class="p_Heading1"><span class="f_Heading1">Stereotypes Profiles</span></p>



  
                </td>
                <td align="right">
                  <a href="introduction.htm" onmouseover="document.images.main.src='button_main_h.gif'" onmouseout="document.images.main.src='button_main.gif'">
                    <img name="main" src="button_main.gif" border=0 alt="Return to Introduction">
                  </a>&nbsp;
    
                  <a href="defining_child_diagram_types.htm" onmouseover="document.images.prev.src='button_prev_h.gif'" onmouseout="document.images.prev.src='button_prev.gif'">
                    <img name=prev src="button_prev.gif" border=0 alt="Previous page" />
                  </a>&nbsp;
    
    
    
                  <a href="quick_linker_definitions.htm" onmouseover="document.images.next.src='button_next_h.gif'" onmouseout="document.images.next.src='button_next.gif'">
                    <img name=next src="button_next.gif" border=0 alt="Next page" />
                  </a>
    
    
                </td>
              </tr>
            </table>
          </div>
          <div id="mainbody">
  


                <p class="p_BodyText"><span class="f_BodyText">In Enterprise Architect 6, an MDG Technology could consist of many UML Profiles, each representing an Enterprise Architect UML </span><span class="f_UIControl">Toolbox</span><span class="f_BodyText"> page. Each profile could include stereotype definitions alongside redefinitions of standard UML elements. This meant that to define a stereotype in a technology, it had to appear in one of the</span><span class="f_UIControl"> Toolbox</span><span class="f_BodyText"> pages.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Enterprise Architect 7 takes a different approach, splitting the task of defining the stereotypes and the task of defining the </span><span class="f_UIControl">Toolbox</span><span class="f_BodyText"> pages into separate profiles. The MDG Technology's stereotypes are contained in one or more profiles. The stereotypes within each profile use the profile name as the namespace.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Create one or more packages with the </span><span class="f_BodyText">&laquo;</span><span class="f_BodyText" style="font-style: italic;">profile</span><span class="f_BodyText">&raquo;</span><span class="f_BodyText"> stereotype, each package name being the namespace. Within each package create profile diagrams defining all the stereotypes in the namespace. You can use multiple diagrams to do this, but do not use nested packages.</span></p>
<p class="p_BodyText"><span class="f_BodyText">Give the </span><span class="f_BodyText">&laquo;</span><span class="f_BodyText" style="font-style: italic;">profile</span><span class="f_BodyText">&raquo;</span><span class="f_BodyText"> package a description in the </span><span class="f_MenuKeyField">Notes</span><span class="f_BodyText"> field (eg </span><span class="f_BodyText" style="font-style: italic;">MDG Technology for BPMN</span><span class="f_BodyText">). When all of the stereotypes are defined (make sure that every stereotype extends at least one </span><span class="f_BodyText" style="font-style: italic;">Metaclass</span><span class="f_BodyText">) right-click the profile package in the </span><span class="f_UIControl">Project Browser</span><span class="f_BodyText"> and select the </span><span class="f_MenuKeyField">Save Package as UML Profile</span><span class="f_BodyText"> context menu option, then proceed as usual.</span></p>




            </div>
          </div>
        </div>



</div>


</body>
</html>
